Get Transaction By ID/UUID
Use this endpoint to retrieve transaction details using either ID or UUID as a query parameter. These values can be found in the transaction details section of the merchant portal or in the API response. This helps fetch transaction-specific data for auditing, reconciliation, support, or record-keeping purposes.
baseUrl/api/v1/transactions/?id={id}Headers
Authorization: Bearer {{accessToken}}(Include the token obtained from the Authentication API)Content-Type: application/json
- Parameters
- Response
You can use either id or uuid as a query parameter to fetch the transaction:
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | No | The unique transaction ID to fetch |
uuid | string | No | The unique UUID to fetch |
Note: You must provide either
idoruuid. If more than one is provided, the API will prioritize one.
Example Request — By Transaction ID
GET /api/v1/transactions/?id=1004 HTTP/1.1
Authorization: Bearer {{accessToken}}
Content-Type: application/json
Example Request — By UUID
GET /api/v1/transactions/?uuid=123e4567-e89b-12d3-a456-426614174000 HTTP/1.1
Authorization: Bearer {{accessToken}}
Content-Type: application/json
A successful response returns a JSON object with the same structure as the Purchase API response. For a full list of response fields and their descriptions, see the Purchase API documentation.
Example Response
{
"id": 714749,
"amount": 100,
"status": "APPROVED",
"terminal": 3040,
"date": "2026-07-23T20:30:59.367335",
"refNumber": "testone",
"rrn": "620420004668",
"cardType": "mada",
"terminalId": "1560127620231203",
"acquirerCode": "RAJB",
"merchantAr": "313233343536",
"merchantEn": "RAJB Testing NeoLeap",
"addAr": "333231",
"addEn": "KAFD",
"merchantId": "803000000324 ",
"merchantCategoryCode": "3014",
"stan": "004668",
"madaAppVersion": "1.2.63",
"cardSchemeAr": "مدى",
"cardSchemeEn": "mada",
"transactionTypeAr": "شراء",
"transactionTypeEn": "Purchase",
"pan": "442463******9008",
"cardExpiration": "27/02",
"amountAuthorizedValue": "1.00",
"amountAuthorizedAr": "مبلغ الشراء",
"amountAuthorizedEn": "PURCHASE AMOUNT",
"statusMessageAr": "مقبولة",
"statusMessageEn": "APPROVED",
"verificationMethodAr": "لا يتطلب التحقق",
"verificationMethodEn": "NO VERIFICATION REQUIRED",
"approvalCodeAr": "رمز الموافقة",
"approvalCodeEn": "Approval Code",
"approvalCodeValue": "U5MUZ5",
"endDate": "23/07/2026",
"endTime": "20:31:05",
"thanksMessageAr": "شكرا لاستخدامكم مدى",
"thanksMessageEn": "Thank you for using mada",
"saveReceiptMessageAr": "يرجى الاحتفاظ بالفاتورة",
"saveReceiptMessageEn": "please retain receipt",
"entryMode": "CONTACTLESS",
"actionCode": "000",
"applicationIdentifier": "A0000002282010",
"terminalVerificationResult": "0000000000",
"transactionStateInformation": "0000",
"cardholaderVerficationResult": null,
"cryptogramInformationData": null,
"applicationCryptogram": "80",
"kernelId": "03",
"paymentAccountReference": null,
"cashierName": "prodtwo",
"branchName": "Riyadh Main Branch",
"providerResponseCode": "00",
"uuid": "4cefe420-7bf4-4b37-bd1c-aa7692ac3613",
"switchResponseCode": "000",
"startDate": "23/07/2026",
"startTime": "20:31:05",
"totalTime": 7318,
"initiationTime": 0,
"terminalReceiveRequestTime": 1784827858973,
"providerStartTime": 1784827859290,
"providerEndTime": 1784827866111,
"terminalSendResponseTime": 1784827866169
}
Error Handling
If the transaction is not found or another error occurs, you may receive an error response:
Example Error
{
"status": "failed",
"msg": "Transaction not found"
}
Usage Tips
- Token Authorization: Always ensure your token is valid before making a request. Include it in the
Authorizationheader in the format:Authorization: Bearer <accessToken>. - Transaction ID: Use the correct and existing transaction ID to avoid errors.
- Reference: For more details on the response fields, refer to the Purchase API.